The initial goal of moving to an approach of SQLite-first output will require more effort to get a consistent experience.
I had also proposed making sqlite output the default, which we did recently in #32; this change might cause compatibility issues for users who are not aware of the change. So, I propose the following:

• Roll back the default method to the original behavior (CSV wide format output)
• to move all the functions for the SQLite-based output approach to a new script inside the deer-ues-tool package,
• Caution users not to use wildcard queries (*) with this script, which could cause column misalignment when some models lack data for a given query. For gathering normalizing units like cooling capacity, "result.py" works better, anyway.

Here is what the SQLite-first method does now:

• Calling with flag --csv invokes gather_sim_data_to_sqlite_long() followed by export_wide_table_from_sqlite()
• Collects raw data in the same format as in EnergyPlus SQLite output files, allows refreshing next steps
• Automatically names output columns from EnergyPlus results including units
• Avoids column misalignment due to wildcard queries
• Includes DEER peak period demand result
• Implements user-specified column names as in modelkit query
• Handles wildcard queries (*) as an aggregated sum

For reference, here is what we had before introducing the SQLite-first output method:

• Calling no flags invokes both gather_sim_data_to_csv() (wide format)
• Collects raw data in the same format as in EnergyPlus SQLite output files, allows refreshing next steps
• Automatically names output columns from EnergyPlus results including units
• Avoids column misalignment due to wildcard queries
• Includes DEER peak period demand result
• Implements user-specified column names as in modelkit query
• Handles wildcard queries (*) as an aggregated sum